Apply Yard Model Changes to Yard form

Models Yard Models Yard Models view Actions Open Yard Editor Yard Editor view Actions Apply Yard Model Changes To Yard Apply Yard Model Changed To Yard form

Use the Apply Yard Model Changes To Yard option to merge any changes from the edited yard model to the yard model associated with the owning (active) yard. In the Yard Models view (on page 1), the Active column identifies the yard model currently applied.

You must restart XPS and the Bridge daemon and ECN4 services, all of which you shut down before you cloned the yard model (see Revise the yard model (on page 1) for information about the shut down). Therefore, make sure to apply yard model changes only when you are prepared to restart XPS and the Bridge daemon and ECN4 services.

Prerequisites

• You must have the Yard Editor - Apply Yard Model privilege.

To apply yard model changes to the yard:

1. Click Actions Apply Yard Model Changes To Yard.

2. In the Apply Yard Model Changes To Yard form, click Yes to confirm.

The N4 Yard Editor displays a message to perform the index maintenance in the SQL Server database after applying the yard model changes.

3. Click OK. N4 applies the changes.

4. Make sure to restart XPS, the Bridge daemon, and ECN4 services.

When applying the yard model changes, N4:

• creates any missing required logical blocks. For more information, see the table in the Logical Blocks view (on page 1).

• generates and pushes the berths.txt file to the cache so that XPS can load it, just like the yard file, provided that a berth model (on page 1) already exists. For more information, see Automated pushing of berths.txt file to XPS (on page 1). XPS reads the berths.txt file from the shared folder regardless of whether the file came from N4 or if someone manually copied it there. We recommend that you use Yard Editor to setup the berths in N4. However, if you are having problems with the berths setup you can optionally place the berths.txt file in the XPS shared folder.

• verifies that the name of the yard model matches the owning yard. This match verification is essential for XPS to be able to connect to the correct cache. Therefore, while it is possible for a user logged into yard A to load a yard file that actually belongs to yard B, N4 prevents a user from making yard model B active because neither XPS nor ECN4 would be able to start successfully in such a case.

• validates the following naming components and displays the results of these validations in the Validate yard model form (on page 1):

• Bin names: Depending on setting YRDCORE001 (ALLOW_DUP_BIN_NAME_FOR_YARD_SECTIONS) (on page 1), N4 alerts you to any duplicate stack names or stack and section names. To resolve duplicate bin names, you can modify the naming schemes in the block or naming tables. For details see Handle duplicate bin names (on page 1).

• Obsolete bin name tables for both stack blocks and yard sections

• Conflicting block naming schemes

Keep in mind:

• Yard model changes are not applied if the yard model does not include geometry information.

• If the apply yard model changes process fails or is killed, data processed up to the point of termination is persisted to the database.

• If your yard model changes include the reconfiguration of a rail track plan, you must re-spot the railcars of the reconfigured rail track plan. See Update Spotting Status form for re-spotting instructions.

• If N4 encounters any issues while applying the yard model, error reporting happens at a higher level than during an import of the yard model (on page 1). Therefore, the error messages you receive as a result of both actions may differ.

• If Yard Editor returns a null pointer exception error when you apply changes to the yard model, this error may be related to a missing or an inappropriate definition of berth range sequences.

To verify if this is the issue:

1. Go to the Berth Ranges tab (on page 1) in the Berth Model form (on page 1) (Configuration Models Berth Models Berth Models view) and verify that the sequences for your berth ranges are properly defined.

2. Verify that all of the required fields in the Berth Model form include the appropriate data.Because of memory and performance constraints, rollback is not possible.